feat: basic textobjects #109
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @tonyjthomas, I am not quite sure if I think this is the best place for these queries, since they are uniquely tailored to a Neovim plugin. It looks like languages that nvim-treesitter-textobjects support have their queries defined in the nvim-treesitter-textobjects repo itself so I think it would be best to contribute these queries there. |
|
Understood, I'll see about opening a PR there instead. Thanks for the feedback! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements a non-exhaustive set of textobjects, most importantly @function.inner and @function.outer.
First time writing treesitter queries, so please let me know if anything can be improved. Hopefully this is a reasonable starting point that others can add to.